perm filename ROY.MSG[MUD,SYS] blob
sn#548970 filedate 1980-12-13 generic text, type C, neo UTF8
COMMENT ⊗ VALID 00035 PAGES
C REC PAGE DESCRIPTION
C00001 00001
C00005 00002 ∂27-Mar-80 0016 ME automatic hangup
C00011 00003 ∂28-Mar-80 1009 REG
C00012 00004 ∂16-Aug-80 1619 ROB How to check out a DD channel
C00021 00005 ∂24-Aug-80 1711 ME
C00028 00006 ∂24-Aug-80 1906 ME
C00029 00007 ∂25-Aug-80 0902 REG data disk
C00030 00008
C00033 00009 ∂08-Sep-80 2201 PEG Keyboard
C00050 00010 ∂12-Sep-80 2309 ROD IML-21
C00055 00011 ∂26-Sep-80 0827 SIS Olive Oyl
C00066 00012 ∂03-Oct-80 1245 CEC connectors
C00072 00013 ∂07-Oct-80 1148 ROB DCA scanner AS cards
C00076 00014 ∂09-Oct-80 1142 ROB So has TTY57
C00079 00015 ∂09-Oct-80 1219 ME DCA
C00080 00016 ∂09-Oct-80 1820 CLT Datamedia garbling
C00082 00017 ∂10-Oct-80 1432 LES Terminals not responding
C00084 00018 ∂11-Oct-80 1150 LES TTY-3 lossage
C00085 00019 ∂11-Oct-80 1427 ME
C00086 00020 ∂11-Oct-80 1557 REG
C00087 00021 ∂12-Oct-80 1751 ME DD CR problem
C00089 00022 ∂13-Oct-80 1215 ROB
C00093 00023 ∂15-Oct-80 0907 100 : mvw
C00095 00024
C00097 00025 ∂20-Oct-80 0132 ME new special WHO feature, new WAITS documentation file
C00107 00026 ∂22-Oct-80 2126 ME DD 24-char line problem
C00111 00027 ∂27-Oct-80 1214 LES TTY4
C00114 00028 ∂05-Nov-80 0718 REG
C00130 00029 ∂11-Nov-80 1248 HHB
C00141 00030 ∂12-Nov-80 1808 ROY
C00146 00031 ∂14-Nov-80 1730 ME DD channels
C00148 00032
C00151 00033 ∂18-Nov-80 1648 JK
C00152 00034 ∂19-Nov-80 1230 ME it's true that...
C00153 00035 ∂21-Nov-80 1204 ME TTY53
C00159 ENDMK
C⊗;
∂27-Mar-80 0016 ME automatic hangup
To: ROY, ROB
CC: LES, REG
The next version of the system will periodically hang up any phone line
that is not in use (the period is every 12 minutes). This should make it
unnecessary for users ever to hang up a phone with the TTY HANG command,
although that command will still be available (for instance, if perchance
you don't want to wait 12 minutes). I hope this will therefore prevent
the situation that Les described in which apparently about half of the DM
dialup lines were off-hook but not in use. It presumably will also solve
the problem of modems that only "half hang up" when someone calls them and
then hangs up without ever presenting a carrier.
Note that this software hack is to solve some distracting hardware
problems that we don't have time to fix right now. However, this should
not be taken to mean that we should never bother trying to fix the modem
problems that this circumvents, namely, the failure of the modems to hang
up completely when they are not receiving a carrier.
P.S. This periodic hangup will apply to the 300-baud lines as well as the
DM lines, since at least one of the slow lines (TTY37) has been observed
to need hanging up sometimes.
∂28-Mar-80 1009 REG
To: ME
CC: ROY, ROB
re: Hanging up modems.
SCORE and LOTS use the same UDS hardware as SAIL uses. They have no
problem with getting lines that aren't active to hang up.
I think you'd be in much better shape if you'd fix the software:
Leave DTR down until you see RI. Then raise DTR for 30 seconds.
If after 30 seconds there is no carrier, drop DTR again.
Leave DTR up until you see carrier drop. When carrier drops,
hold DTR down for 20 seconds.
∂16-Aug-80 1619 ROB How to check out a DD channel
--------------------
1) .ac (sets your priveledges so you can ATTach and DETach DDs)
Password: (this won't echo when you type)
↑C
2) .ex ddtest[f,rob]
Swapping to SYS:LOADER.DMP
LOADING
LOADER 48 PAGES
EXECUTION
What channel (<cr> for yours, * for all): ↑C (call out of the program)
↑C
3) .att dd32 (attach the DD in question)
4) .s (start the DDTEST program again)
What channel (<cr> for yours, * for all): 32
(Type any character to quit.)Calling PutChan with Chan = 26. GotGhan = 26
'32
(type a return to exit the program)
End of SAIL execution
↑C
5) ..det dd32! (DETach the DD with an "!")
--------------------
You can repeat steps 3-5 as often as you want to test other channels.
- Rob
∂24-Aug-80 1711 ME
To: ROB, ROY
DD chan 33 is getting crosstalk from DD 32.
∂24-Aug-80 1906 ME
The DD is losing on CR's again, at a low but substantial rate.
∂25-Aug-80 0902 REG data disk
If the data disk needs further repairs, please make them.
Otherwise, it should be closed up.
Ralph
∂29-Aug-80 1114 CEC connector cables
Hi. We were wondering about the status of the 40 conductor "berg" type
cables you were making for us. We still need 4 of them, about 15 feet long.
Has the parts come in?
Also, has the student returned the 5v power supply?
Casey
∂08-Sep-80 2201 PEG Keyboard
To: DC, ROY
CC: ME, ROB
The "A" key on the Data Disc keyboard in MJH443 broke tonight. When it is
fixed, could it please be returned to that office? (I took the one in the
shop as a replacement, but it's not very good...)
Thanks-- Phil Gerring
∂12-Sep-80 2309 ROD IML-21
To: ROB, ROY, ME
RWG says that the system has lost IML-21, sometime during ROB's
morning downtime, as that was the last thing on the screen. We
tried "FLUSH TTY21", unexisting it and existing it, but wouldn't
work.
∂26-Sep-80 0827 SIS Olive Oyl
Roy,
Thanks so much for fixing her. She's beautiful and you did
such a great job you would never know she lost her head!
You made my day! I'm very sentimental about her, and now
you're part of her history too.
Thanks again,
Sue
∂03-Oct-80 1245 CEC connectors
We were wondering about the status on the 6 connector sockets you ordered
for us so you could make us some cables to run between our DR11-C's.
Has it arrived yet?
casey
∂07-Oct-80 1148 ROB DCA scanner AS cards
To: ROY
CC: ME, REG, ROB
Roy:
By my current count, there are six AS cards in the DCA which have red tags
on them. Five of them are "spares", and one of them is stolen from an
(otherwise) unused slot. I have an untested hypothesis that at least one
more AS card is acting up (the one for TTY57). I'm not sure we have any
other AS cards that can be swapped around, so we should get some fixed as
quickly as possible.
I talked to DCA and was told that If we send DCA the sick AS cards along
with a PO number, they will concurently send us some shiny new AS cards
for replacement.
You can write up a PO requisition, give it to Susan Hill and let her know
that it's urgent. She can arrange to have purchasing tell us the PO
number when it goes through, then you can call DCA and give it to them
verbally. (Be sure to tell Susan that's what you plan to do.)
Some names and numbers:
Digital Communications Associates
BPHONE 404 448-1400
BADDRES 125 Technology Park/Atlanta ⊗ Norcross, GA 30092
CONTACT Dave Hendrickson ⊗ Technical Services
The bureaucratic wheels grind onwards...
- Rob
∂09-Oct-80 1142 ROB So has TTY57
To: ME, ROY
∂08-Oct-80 1036 MFP Bad TTY
To: ROB, ME
My hardwired TTY line (56) has stopped working.
∂09-Oct-80 1219 ME DCA
To: ROB, ROY
∂09-Oct-80 1142 ROB So has TTY57
To: ME, ROY
∂08-Oct-80 1036 MFP Bad TTY
To: ROB, ME
My hardwired TTY line (56) has stopped working.
ME - On Tues, I swapped DCA port cards for 56/57 and 34/35 (unused).
TTY57 didn't work before or after the swap.
∂09-Oct-80 1820 CLT Datamedia garbling
To: ROY, ROB, ME
The following phenomena occur with distressing regularity when talking
to WAITS via the DATAmedia
Sequences of characters from one place appear at another place on the screen
Lines disappear
The whole screen disappears
Lines (other than the one currently being typed) garbage
Garbage appears in the line being typed.
I type one character, another is printed.
When trying to insert in the middle of a line it appears that the insertion
is being done at a position offset from the actual insertion.
etcetera, etcetera and so forth!
Doing anything that causes the screen to be rewritten temporarily restores
it to a coherent state.
Is the above the usual behaviour of DMs? or is mine ill. If the former,
how do people put up with it? If the latter, what do I do to get it fixed.
(I have tried dialing other than 81, but seems always to behave badly.)
∂10-Oct-80 1432 LES Terminals not responding
To: ROY, ROB
CC: REG
Two terminals that I just tried to log in on show no response to keystrokes
of various sorts -- they just keep displaying "TAKE ME I'M YOURS".
This happened on the public terminal at the back of room 460 and in
LTP's office (room 342). Meanwhile, everthing else seems to work.
∂11-Oct-80 1150 LES TTY-3 lossage
To: ME, ROB, ROY
CC: REG
I have used the new UDS modem on several 1200/150 lines and find it to
be quite solid except for TTY-3, which has an unacceptable error rate
in the computer → display direction. The evidence strongly suggests
that the line is substandard in some way, possibly too much crosstalk.
It would be nice if it could be established that the line does not meet
specifications in some way, but I realize that may be tough to prove. In
any case, I suggest that TPC be asked to fix it or provide a different
pair.
∂11-Oct-80 1427 ME
To: LES
CC: ROB, ROY, REG
TTY3 has given us trouble all along, but we suspect that the problem
is crosstalk in our own cable. I have been trying to get someone to
look into it off and on now for 6 months.
∂11-Oct-80 1557 REG
To: ME, LES, ROB, ROY
TWIMC:
I've just changed these modems so that
0085 connects to TTY3
0083 connects to TTY5
If the crosstalk moves to TTY5 it's the phone line.
If it stays on TTY3 it's the local wiring.
∂12-Oct-80 1751 ME DD CR problem
To: ROB, ROY
It seems to like to be tickled by lines 79 chars long, as well as lines 20 chars
long, although in the former case, it seems to depend on which characters appear
in the 79-character line!
∂13-Oct-80 1215 ROB
To: ROY
CC: ME, REG, LES
∂11-Oct-80 1150 LES TTY-3 lossage
To: ME, ROB, ROY
CC: REG
I have used the new UDS modem on several 1200/150 lines and find it to
be quite solid except for TTY-3, which has an unacceptable error rate
in the computer → display direction. The evidence strongly suggests
that the line is substandard in some way, possibly too much crosstalk.
It would be nice if it could be established that the line does not meet
specifications in some way, but I realize that may be tough to prove. In
any case, I suggest that TPC be asked to fix it or provide a different
pair.
--------------------
ROB - This could be a problem with the transmit gain in the (local) UDS
modem card. It is adjustable, and should be tweaked whenever the modem
card is moved. (The overload light on the DAAs tell you when there is
too much gain.)
∂15-Oct-80 0907 100 : mvw
call Don Smith at HEPA Corp 714-630-5700
∂15-Oct-80 1954 ME DCA port 57
To: ROB, ROY
doesn't seem to work even with a card that works on port 55.
However, there also was a bad card in slot 57 (the second such bad
card, this one wouldn't transmit chars to the Canon), which I have
red-tagged, although I guess I'll leave it in slot 56/57 since the
port 56 half seems to work (and is used). Thus both port 57 and
about 8 AS cards now seem to need repair.
∂20-Oct-80 0132 ME new special WHO feature, new WAITS documentation file
To: "@W.DIS[1,ME]" at SU-AI
The new file WIZARD.TXT[SS,SYS] has been created to hold various pieces of
special documentation about WAITS that are of interest basically only to
system programmers. At the moment there is little in that file, although
I hope to see it grow.
One new feature of the WHO program IS documented in this new file (only),
namely, the ability to display the contents of one or more WAITS system
tables. WHO is much more convenient than UEDDT for watching system
parameters change, even if you are watching only one such value. The
WIZARD.TXT[SS,SYS] file documents this feature, which uses W ! or the αβ!
command to select table-display mode and +<symbol><cr> to display the
table (cell) whose name is <symbol>. See documentation for more details.
I hope to expand WIZARD.TXT to include all the common techniques of
managing the system. Other peoples' contributions or suggestions for
inclusions will be gladly accepted. I don't expect this to be a
high priority item, but this file provides a place to record anything
that may be of use to future (and present) system programmers,
whenever such information happens to be found or needed online.
∂22-Oct-80 2126 ME DD 24-char line problem
To: ROB, ROY
I have modified DART to type out an extra space on each line so
that the line is not exactly 24-chars long. I hope the bug doesn't
last so long that other programs end up getting kludged up that way.
I got tired of not being able to read the stuff that Dart was typing out.
∂27-Oct-80 1214 LES TTY4
To: REG, ME, ROY, ROB
I notice that TTY4, which used to work quite well with the crufty old modem,
has a substantial error rate with the new one in the computer → display
direction. The errors mostly come in bursts of a dozen or so characters.
!∂$@\\∀∃$%#@&!!
∂05-Nov-80 0718 REG
To: csd.hill at SU-SCORE
CC: ROY at SU-AI, ROB at SU-AI
∂04-Nov-80 1244 Susan Hill <CSD.HILL at SU-SCORE> Clayton Mock
Date: 4 Nov 1980 1239-PST
From: Susan Hill <CSD.HILL at SU-SCORE>
Subject: Clayton Mock
To: reg at SU-SCORE
This is reminder to speak to Clayton Mock about his calls to Hawaii from Don Coates'
phone. How do you suppose he did that without an authorization code? They
cost about $l5. Susan
------
An unrestricted phone can place calls outside the 48 states without an
authorization code, because the WATS lines only cover that area.
Does Mary have a check for him? Let's leave a note on it, if so.
Ralph
∂11-Nov-80 1248 HHB
To: RDA at SU-AI, AAM at SU-AI, ML at SU-AI, BIS at SU-AI,
TOB at SU-AI, JKS at SU-AI, CG at SU-AI, PB at SU-AI, MAS at SU-AI,
ARG at SU-AI, ROY at SU-AI, ROB at SU-AI, CR at SU-AI,
PLS at SU-AI, BOLLES at SRI-KL, GASCHNIG at SRI-KL
PARTY PARTY
You are invited to a
POTLUCK DINNER
and PARTY
at the home of
JIM DAVIDSON STEVE TAPPEL HARLYN BAKER
2405 Laura Lane, Mountain View (965-9352)
Saturday November 15
potluck dinner at 6:30
or come after 8:00 for just the party
friends welcome
| |
| San Antonio |
----+--------------------------------+------ ↑ North, more or less
| |
| |
| |
| Alma /|
| / |
| / | Middlefield
| -\ | |
| | Laura | |
| | | |
| x| | West Middlefield
+-----------+----------\ | |
| Thompson | | |
| Junction| | |
| | | |
----+----------------------+-----+---+------
| Rengstorff | |
| | |
| | |
∂12-Nov-80 1808 ROY
getting it over with
Dear Roy,
This friend of mine keeps bugging me about it so I thought I better ask you
or I'll never get any homework done...
If you still need a debugger or troubleshooting techie, I know I have the
person for you. Her name is Celia Chin (yes, female, but she's okay...in
fact very good). She is a Senior EE/CS major about to enter coterminal
studies...just another indicator of her remarkable academic achievements.
She's very bright, and eager to learn (learn what?...I dunno cuz she seems
to know everything already). Personality-wise, she is really nice and I
like her a lot (PROFESSIONALLY). I believe she has already completed all
of her major EE requirements with the highest achievement. She has experience
in programming in SAIL (one of the very few people I know who can program in
this academically archaic language...but I believe is used here quite often),
ALGOL, and I think FORTRAN. Work experience is long, but for example, this
past summer, she has worked at Vydec, a subsidiary of EXXON, as a full
electronic technician doing debugging, testing, troubleshooting and assembling
prototypes...etc...etc...etc. I believe you will find few people who can have
as much experience as she does in so many fields of electrical engineering...
academic, programming, both hardware and software.
If you think I am trying to recommend her...you're right!...Hey! Anyway, though
she would prefer to do software...systems programming, I am sure she can also
handle and do the less peonic jobs here like the troubleshooting and testing you
need done. Maybe she may even be able to give a lesser skilled technician (hint
hint) some much needed training so he can someday be able to do some creative,
thought-necessary work for a change???
{h well, but this is a suggestion, and if you still need someone...maybe you do,
then I think she is more than able for the job. CHECK HER OUT! (no joke intended)
try writing me by SCORE mail or I'll see you whenever...nice day!...Clay
∂14-Nov-80 1730 ME DD channels
To: ROD, ROB, ROY
∂14-Nov-80 1634 ROB
∂14-Nov-80 1558 ROD
DD33 is detached from system, but looks in pretty good shape (32 looks not bad)
ME - OK, I've re-attached 24 and 33, but 32 and 37 have only one field working,
so they're still detached.
∂18-Nov-80 0133 ME TTY14 (DM line, DCA port 14)
To: ROY, REG, ME
... seems to have Carrier Detect bouncing up and down rapidly, generating
lots of interrupts (except that I did a TTY NO EXIST 14 to stop it now).
∂18-Nov-80 1648 JK
Ralph Gorin tells me that you are the person who is supposed
to install the other terminal in the Doyle-Ketonen office.
When will this take place?
∂19-Nov-80 1230 ME it's true that...
∂18-Nov-80 0047 DCL Luckham's line down
To: ME
CC: REG
Marty,
My line is not responding; clicks but no signal.
- David
∂21-Nov-80 1204 ME TTY53
To: ARG
CC: ROY
∂20-Nov-80 1354 ARG TTY53?
To: ROY, ME
TTY53 doesn't seem to be working. It's probably just that the cable connecting
the terminal box to our DZ11 isn't right; it probably needs to swap receive &
transmit at one end. (Does that make sense?) However since the 10 doesn't seem
to know that TTY53 exists (I did a TTY EXIST for it, but is that enough?) maybe
there's something on the 10's end that needs to be done?
thanks, Ron
ME - You can try setting the speed with TTY TTY53 SPEED 1200 (or whatever).
I have just now changed the default speed for 53 to 1200 (I think it was 2400).
TTY EXIST resets the speed to the default, so TTY EXIST 53 should be sufficient
now (unless the wiring isn't correct).
∂21-Nov-80 1555 100 : TTY53 TTY53
To: ROY, LS
IT WORKS!!!! YAY!
∂21-Nov-80 1634 WP terminal installation in ERL
If I am not in my office on Monday morning please get the key
from Jenny in ERL 235b (the other room I showed you).
wolf
∂23-Nov-80 1328 JK dm upgrade
To: ME
CC: JMC, ROY
I will bring my DM to Product Associates as soon as the second
terminal is installed in my office: Right now I am in the
middle of debugging a large formal reasoning system for JMC
and need fairly good access to the system. Since ROY has
promised to install the terminal in the very near futre I
don't expect this to cause much delay.
I will send you a message immediately after I delivered the DM to
Product Associates. If you have the directions somewhere around
I would appreciate getting them again: It seems that I have
deleted that message.
∂24-Nov-80 1220 LES Apparent hardware bug
To: ROB, ROY
CC: REG, ME
There was apparently an undetected memory or CPU error a few minutes ago.
I was PUBbing and got "Illegal instruction [xxx] at user 436644" but neglected
to write down the "xxx". When I repeated the PUB command, it executed
successfully to conclusion.
∂24-Nov-80 2217 ME A brief experiment has just shown that TTY2's modem fails to hang up when
it loses the remote carrier. After that, it appears free at the computer,
but is busy on the phone and calls to it go on to TTY3 and on up. Could
you have a look at the modem? Thanks.
∂28-Nov-80 2013 REG
To: ME, ROY, ROB
.pub b
Swapping to SYS:PUB.DMP
B.PUB 2 3 4 5 6 7 8 9 10 11 12 13 14 15 16 17 18 19 20 21 22 23 24 25 26
27 28 29 30 31 32 33? Error in job 41
Illegal UUO (0) at user 520534
↑C
.e 520534
520534/ 271240 21 .e 520530
520530/ 542043 0 .e
520531/ 202103 1 .e
520532/ 254000 512615 .e
520533/ 322240 520575 .e
520534/ 271240 21 .r ddt
SDDT$: 271000,,;ADDI 0 322000,,;JUMPE 0
↑C
↑C
.r ppsav
Don't look like an illegal UUO to me. Especially, it wasn't zero.
What do you suppose happened?
∂28-Nov-80 2017 REG Location indeterminate parity errors
To: ROB, ROY, ME
I notice that there's an SBUS error (MB parity) at 18:31 tonight
that probably corresponds to my previous message.
At least the last three address digits were 537 which is close
enough to the 534 that it complained of.
Looks as though the code in WAITS isn't paranoid enough to
recover good data in such circumstances....
∂28-Nov-80 2333 ME SBUS errors
To: REG
CC: ROB, ROY
∂28-Nov-80 2017 REG Location indeterminate parity errors
To: ROB, ROY, ME
I notice that there's an SBUS error (MB parity) at 18:31 tonight
that probably corresponds to my previous message.
At least the last three address digits were 537 which is close
enough to the 534 that it complained of.
Looks as though the code in WAITS isn't paranoid enough to
recover good data in such circumstances....
ME - Are you suggesting that WAITS read the location two or three times if
it doesn't get a good thing the first time? The parity error probably
caused the memory to return a bad parity 0 initially, but thereafter it
returned the right value. The zero printed is the UUO that was stored by
the KL when it trapped. I wish the hardware wouldn't do these things
(SBUS error indeed).
∂29-Nov-80 0918 REG
To: ME, ROB, ROY
∂28-Nov-80 2333 ME SBUS errors
To: REG
CC: ROB, ROY
∂28-Nov-80 2017 REG Location indeterminate parity errors
To: ROB, ROY, ME
I notice that there's an SBUS error (MB parity) at 18:31 tonight
that probably corresponds to my previous message.
At least the last three address digits were 537 which is close
enough to the 534 that it complained of.
Looks as though the code in WAITS isn't paranoid enough to
recover good data in such circumstances....
ME - Are you suggesting that WAITS read the location two or three times if
it doesn't get a good thing the first time? The parity error probably
caused the memory to return a bad parity 0 initially, but thereafter it
returned the right value. The zero printed is the UUO that was stored by
the KL when it trapped. I wish the hardware wouldn't do these things
(SBUS error indeed).
----
An SBUS error indicates a bad memory word was read, and identifies
within 4 locations the bad word. WAITS could determine who that physical
page belongs to and stop that job, annoucing that a parity error occurred,
even though it wasn't solid.
The parity error was probably caused by the memory returning nothing
initially. I wonder why it does that.
Ralph
∂01-Dec-80 1336 ME
Jake has a broken DM in her office that you should pick up and
think about fixing. She said "Denny thought it was the picture tube".
∂01-Dec-80 1539 Denny Brown <CSD.DBROWN at SU-SCORE> broken DM terminal
Date: 1 Dec 1980 1538-PST
From: Denny Brown <CSD.DBROWN at SU-SCORE>
Stanford-Phone: (415) 497-2274
Subject: broken DM terminal
To: me at SU-AI, roy at SU-AI, rob at SU-AI
cc: csd.jake at SU-SCORE
The terminal which I normally have at home is in Jake's office (215).
The screen is always blank. No cursor, etc. Blown "picture tube"?
Jake was supposed to ask somebody about fixing it; I don't know who
she talked to or when, but it's still in her office. I'm not in a
tremendous hurry, but I'm worried about it getting ripped off, since
that office is always open. -Denny
-------
∂03-Dec-80 1936 ME NYT wire
To: ROB, ROY
Could you look to see if there is some reason why the NYT box should not
be receiving anything? Like if it is somehow disconnected. I don't know
where the wires feeding it come from, but the box itself is not blinking
(its fuse is OK and it has power).
∂07-Dec-80 0106 ROD l→→d
To: ROY, ROB
On the keyboard at TV-123 (my office - 030a - furtherest from the door)
"l"s are often getting heard as "d"s. Are one of you who I should tell?
∂10-Dec-80 1815 JMC problems
To: ROY
CC: REG
1. You were going to do something about my Datadisc.
2. Weyhrauch's Imlac has been down for many months, and I understand
that the problem is with the line or at this end. Should I give up
and give him a Datamedia?
∂13-Dec-80 1604 WP
What's happening with the line to ERL?